Browse Prior Art Database

Real Time Accessibility Disclosure Number: IPCOM000242575D
Publication Date: 2015-Jul-28
Document File: 3 page(s) / 229K

Publishing Venue

The Prior Art Database


Currently, a lot of software companies run automated testers, in-browser extensions for single page testing, and/or a testing suite for software accessibility capabilities. The inherent problem with all of these existing solutions is that they require developers to go back to their code and integrate accessibility issues after they have already contributed to their projects. The steps are usually as follows: - Developer contributes code in project - After some testing, accessibility issues arise - The issues are documented - The issues are added to a mixed bucket of other development to do lists - The developers that might or might not originally have worked on the code start integrating fixes, and it is not guaranteed for the developers to be knowledgable about software accessibility. - The fixes are usually crude and not in context of the software unless a dedicated accessibility designer and/or developer contribute to the fixes. Remediating code issues, whether it be bugs, security vulnerabilities or accessibility problems, is not only a complex communication issue, but it is difficult to actually implement. The disclosed will review how these issues can be fixed by introducing a system and method that can alleviate some of the pointed complications, as well as a new workflow for developers.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 51% of the total text.

Page 01 of 3

Reax Time Accessibility

Presently most software that is run on a web browser has either lack luster accessibility experience or it xx insufficient in accessixility in genxral. The inherit issue of these prxblems is a stacking xssue. Often, inadequate accessibxlity integratiox xolutions use accessibility xcanners/testers that either surface problems after the pxoject is running WAVE Wxb Accessibility Tool) or thx problems xre repxrted by batchxs in x report format. Each issue requirex a person to understand, formulatx a solxtion, and pxioritize thx reported issues before sending it to the apxropriaxe develoxers to be intexrated.

Another prxblem arises when developers recxive the accessibility issue and they do not

have the cxntext to ixtegrate the accessibility isxue/content properly.

The proposed invention would metaphorxcally be the "software accessibxlity spell checker". This invxntion allows developers to surface and reveal thxir accessibility issues in real time whxle they axe xoding in their text editor/integrated development environment, long before the code is integraxed into a project axd/or any introduced xo x testing envirxnxent. The surfaced issues are prioritized by x weightxd severity that is scored from a sextable company policy, wxich allows the developexs to self prioritize what is xosx important. When the developer focuses on a specific issxe or set of issues, they are provided with an explanatixn of what txe problem is, how to fix it, and further documentation on the issue from reputable sources suxh as the World Wide Web Consortium.

Below is a before and after rxpxesentation of the idea.