StandardWeb has been developed to obtain at minimum the WCAG 2.0 Level A conformance.
This means that every content inserted by users is processed by the software to remove or to report any non compliant circumnstance.
The final result is that each webpage dynamically builded by the software will be compliant at least with one of the most important accessibility rule: the formal validity of the code language (4.1.1).
StandardWeb satisfies the following WCAG 2.0 criteria:
First principle: Perceivable
- 1.1.1: Every image, every control, every textbox or every other non textual content generated by software has a text alternative. The content creator can provide further text description but if he does not, the software provides itself to correct the issue. Every graphic formatting and every decoration are inserted by CSS and doesn’t impact in any way to the markup.
- 1.3.1: The structure of information presentation follows a sequence programmatically predetermined and content creator cannot affect it.
- 1.3.2: The presented information sequence is programmatically predetermined. This doesn’t affect the meaning even if the final user browse the page with non-conventional browser such as Braille monitors or screen reader.
- 1.3.3: The interface’s command are provided using different way that not relies uniquely on a type of sense.
- 1.4.1: Colors are not used as the only method to provide information. Colors and formatting aspect of each XHTML element can be determined by CSS.
- 1.4.2: No audio plays automatically when the webpage is reached by the final user. If audio is included the final user is able to control the playback.
Second principle: Operable
- 2.1.1: All operations and functionality of web user interface can be operable using a keyboard and not only a mouse.
- 2.1.2: The focus on each element of the page can be moved by using the keyboard. No element traps the focus inside him such can be done by textbox or textarea.
- 2.4.1: A system of fixed hyperlinks is provided to bypass repeated blocks of content inside every page.
- 2.4.2: Every page has a distinctive title that describes the page’s main content or the content of the selected category if there are more than one important content in one page.
- 2.4.3: Each page element can receive focus using a keyboard and the focus sequence is not affected by layout. Layout could be changed by final user but this doesn’t affect the meaning and operability of interface.
- 2.4.4: Every hyperlink generated by software has a contextual meaning. An instrument to provide the same feature is provided to content creator to simplify insertion of meaningful hyperlink.
Third principle: Understandable
- 3.1.1: The default language of the page is predetermined by content creator. The software interface automatically retrieves the final user’s browser language and provides the appropriate instructions set.
- 3.2.1: Any element of the page receiving focus starts a change of context.
- 3.2.2: Every element of the page used as input doesn’t start a change of context.
- 3.3.1: If final user receives an error inserting some content, the interface identifies the error and provides a textual description to the user.
- 3.3.2: Every required user input is provided with labels and textual instruction.
Fourth principle: Robust
- 4.1.1: The final software output is provided as XHTML 1.0 Strict page. Every auto generated page can be checked by W3C validator to verify the formal conformance to the specification. The pages are conformant with each inserted content.
- 4.1.2: Every component of generated page has a name and a role programmatically determined. Each area of the page can be easily identified.