Show Menu

High Level Accessibility Requirements Cheat Sheet (DRAFT) by [deleted]


This is a draft cheat sheet. It is a work in progress and is not finished yet.


Ten requir­ements must be met in order to achieve access­ibi­lity, and it is further recomm­ended that:U­ser­-cu­sto­mis­ation at the applic­ati­on/­int­erface level is included whenever beneficial for usability and access­ibility

Attention is applied at the design and implem­ent­ation stages to the naviga­tional flow and contextual feedback mechanisms – these must be logical and, where needed, modifi­cations made to make them more accessible

Applic­ations, interface components and display items are user-t­ested with partic­ipants that include users of adaptive techno­logy. This is important if access­ibility is to be truly realised. User testing may become a requir­ement in the future.

In the following section the ten high level access­ibility requir­ements are expanded into a number of specific checkp­oints.


The following high level requir­ements were derived from an analysis of existing publicly available documents that pertain to the access­ibility of desktop and web applic­ations; for justif­ica­tions and explan­ations, see Design Guidance – Access­ibility Principles {R1}:

1. Support standard system size, colour, font, input settings, and access­ibility options.
2. Enable progra­mmatic access to user interface elements and text.
3. Provide keyboard access to all features.
4. Expose the location of the keyboard focus.
5. Provide equiva­lents for non-text elements.
6. Do not rely exclus­ively on a single perceptual capability to convey inform­ation.
7. Avoid flashing elements.
8. Enable user control of timed inform­ation presen­tation and responses.
9. Ensure consis­tency between interface elements and display items.
10. Create accessible docume­ntation about access­ibility features.