To help us make the The Arc’s Blog a positive place for everyone, we’ve been using the Web Content Accessibility Guidelines (WCAG) 2.0. These guidelines explain how to make web content more accessible for people with disabilities, and user friendly for everyone.
The guidelines have three levels of accessibility (A, AA and AAA). We’ve chosen Level AA as the target for the TheArc’s Blog.
How are we doing?
We’re working hard to achieve our goal of Level AA accessibility, but we realise there are some areas that still need improving. The following information explains what we’re doing to make that happen.
3.3.3: Form Error Suggestion
Yes, all error messages provide suggestions to the end user.
3.3.4: Error Prevention (Legal, Financial, Data)
Yes, all donation forms and payment forms can be reviewed before final submission.
3.2.3: Consistent Navigation
Yes, all navigation systems appear in consistent locations throughout the site.
3.2.4: Consistent Identification of sub navigation items
Yes. Our website identifies consistently navigation, sub-navigation and footer navigation items.
2.4.5: Multiple Ways for a page to be displayed
Yes, all of the pages use adaptable layouts.
2.4.7: Focus Visible on form fields
Yes, you can see the focus ring on all elements as you tab through the page.
2.4.6: Headings and Labels
Yes, all headings are descriptive.
1.4.3: Contrast (Minimum)
Yes, all color combinations meet the AA requirements.
1.4.4: Resize text
Yes, we have this functionality on all pages on the site.
3.3.1: Error Identification
Yes, all errors are identified and described in the user text.
3.3.2: Labels or Instructions
Yes, all labels provide instructions when a user action is required.
3.2.1: Dynamic content change, on focus
Yes, content changes on focus.
3.2.2 Dynamic content change, on input
We do not have any automatic changes of context on the site.
3.1.1: Language of Page
Yes each page has the default language set for screen reader capabilities.
2.4.4: Link Purpose (In Context)
Yes, all links are descriptive, we do not use links that use words like “Click here” but rather we use descriptive titles and alt tags.
2.1.2: No Keyboard Trap
Yes, using the tab key the focus can be removed from any form field.
All content can be tabbed through in the proper order using the tab key.
2.4.3: Focus Order
Yes, all tab indexes follow a logical path preserving meaning and operability.
2.4.2: Page Titled
Yes, all pages have a title that describes topic and purpose.
2.4.1: Bypass Blocks
Yes, you can tab through all content on the site and can be used as a method of bypassing and or skipping content.
3.1.2: Language of Parts
Yes, all language settings have been identified for screen reader purposes.
1.4.2: Audio Control
Yes, audio controls exist on all pages where audio is embedded. Audio can also be stopped by screen readers and as a browser control.
1.4.1: Use of Color
Yes, we use words to convey the importance or severity of content on the site as well as colors.
1.3.3: Sensory Characteristics
Any place where there is a video or a form there are clear instructions on how to play and submit the form on the website.
1.3.2: Meaningful Sequence
Yes, our content displays correctly in all screen readers programmatically.
1.3.1: Info and Relationships
Yes, we meet this criteria. All information is structured and relationships between them are conveyed correctly in the markup language.
Let us know what you think
If you enjoyed using the The Arc’s Blog, or if you had trouble with any part of it, please get in touch. We’d like to hear from you in any of the following ways: