Accessible design checklist

At Sage, we use an wieldy diamond weightier practice checklist to ensure we are making our products and communications wieldy for all types of users. It is vital that our designers consider serviceability from the start of the diamond process, and throughout minutiae at Sage – considering as many angles as possible to include users of varying abilities.

We ensure that as much of this information as possible is passed to the people who build our Sage products and for our website so that we can create wieldy experiences.

Our serviceability checklist is continually reviewed versus Web Content Serviceability Guidelines (WCAG) to prevent pages, patterns, or components rhadamanthine inaccessible.

We encourage using our checklist as part of your own diamond process, to help make your designs increasingly wieldy for all.

Labelling and displaying content

It is important to consider how all on-page content is presented to users. For example, images, buttons, and form fields will require you to take uneaten steps to make these increasingly accessible. The unelevated points should be included:

• All buttons with icons should have a visible text label
• Images should have a text volitional that virtuously describes the content or meaning of the image
• Avoid describing components or on-page elements by position, colour, size, shape, etc
• Display all content on-page i.e. not subconscious in tooltips
• Designs must be responsive to viewport size – this should worth for user behaviours such as zooming in, applying custom styles for text spacing, and variegated device or window sizes
• Dynamically updated content will need to be communicated to screen reader users
• Content like pop-up messages should not disappear until the user dismisses it
• *Use vertically ‘stacked’ or listed form labels such as hints/help, error, and input layout
• Avoid ‘placeholder’ text inside form inputs; expressly for labels or hint/help text

Formatting and styling content

Formatting and styling on pages can be distracting or may dilute messages. It’s important to ensure that your designs consider format and styling elements when making content inclusive for users with varying serviceability needs.

• Use sentence specimen text for labels and headings, rather than title specimen or all-caps
• Consider how the information will be presented and marked up. For example, is the information largest presented as a table or a list, and is this stuff marked up with the correct Schema?
• Do not rely on colour to communicate meaning
• Text and other user interface (UI) elements must have a sufficient colour unrelatedness between their backgrounds and proximal text and/or elements
• Buttons must not squint like links, and links should moreover not squint like buttons
• Always trammels your designs with a colour unawareness filter to ensure it is still readable

Navigation and user experience

Many users with physical, motor, and cognitive disabilities often use the to navigate. This is often in place of a touchscreen, track pad, or mouse. For this reason, we must ensure that everything we produce, from digital products to web pages and communications, are wieldy to keyboard-only. This allows users to perform tasks like browsing or clicking through content increasingly easily, using the functionality of a keyboard to wangle the content as intended. When creating components, the unelevated points should be considered:

• All components are configured to be accessed via keyboard reader
• When using the tab key to navigate buttons, links, and form fields, ensure the order of focus is expected, and the focus indicator is unmistakably visible.
• Keyboard shortcuts should use modifier keys
• Drag and waif functionality should be an enhancement of a button-based mechanism for reordering – and not the only way to reorder
• Target sizes should be 44px × 44px wherever possible; 24px × 24px at a minimum
• Navigation can be skipped by keyboard users
• Page titles must describe what is on each page
• Navigation must be resulting from page to page
• Components that do the same thing must squint and work in the same way
• Ensure multiple ways to navigate from page to page (for example, navigation and on-page links)
• Page content should not transpiration significantly when a form element value (like a radio button) is changed
• Page content should not transpiration significantly when an element receives focus
• Related content and controls must be grouped closely to help users know that they’re available, if using screen magnification
• Headings must be used to help the user identify groups of content on a page
• Links, headings, buttons, and form field labels must be descriptive
• Links must be underlined

Prompts for form or task completion

Accessibility for in-product or on-page task completion is crucial to ensure that errors are minimised for users who may have disabilities that make inputting data increasingly challenging. Accessibly seated prompts for form submission or input fields can help all users interact with these components as intended, permitting them to provide increasingly accurate, correct information.

• Errors must be flagged using text
• Suggestions can be given within error messages to help the user well-constructed their task
• Help and hint text must be used where necessary
• Notifications or flagging should be used to help users trammels and personize important information surpassing submitting
• Supporting content or help resources should be wieldy from every page, should the user need it

Audio, visual, and turned-on on-page elements

When including interactive on-page elements such as audio files, video content, or animations, uneaten considerations will be needed to make these wieldy to all users.

• All videos must have captions
• Include sealed captions and transcripts, and audio descriptions
• Auto-playing animations or video content should have the worthiness to be paused
• Flashes in video or volatility should be kept to a minimum, or avoided completely
• A static volitional to any turned-on illustrations should be designed and included in the resources for development

The whilom checklist has been created in line with the WCAG (Web Content Serviceability Guidelines), 2.0, Level AA and was last updated in September 2022. We ensure that all of our Sage products and web pages are aligned with this checklist to largest serve our Sage customers.

For remoter information well-nigh our serviceability pledge at Sage, throne to our serviceability hub to find out increasingly well-nigh what we do. For notes on our specific products, please view our accessibility statements.

The post Accessible diamond checklist appeared first on Sage Advice United Kingdom.