Creating accessible packages extends on accessibility in an Umbraco context .
The Umbraco UI components have been built to be accessible and have accessibility tests built within them. Building the user interface (UI) using these Umbraco UI components ensures that the package is as accessible as the Umbraco backoffice.
In addition, any fixes and updates to the UI components will be pushed through to the packages when you rebuild them with the updates.
Accessibility testing is more a specialist skillset than it is automated testing. The purpose of this document is to outline what can be done to help build accessible packages. It is not a complete list of accessibility tests that can be performed.
Build the components using the Umbraco UI components as these have accessibility tests built within them.
Use the keyboard to tab through the elements on the page checking:
Does the element tabbed to have a focus state?
Does the tab order make sense?
Check the UI with a screen reader.
Install an accessibility testing tool as a plugin into your browser to run automated tests:
Tools like axe DevTools are built to reduce the number of false positives in a test.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4