Amanda Durkan Writes is intended to be usable by as many people as reasonably possible, regardless of disability, device, browser or assistive technology.
The site is being developed with the Web Content Accessibility Guidelines in mind. The current goal is to meet WCAG 2.2 Level AA where reasonably possible.
The site has not undergone a complete independent accessibility audit, so no claim of full conformance is currently made.
Accessibility measures
Work carried out on the site includes:
- semantic headings and page landmarks;
- keyboard-accessible navigation;
- visible keyboard focus indicators;
- labelled forms and controls;
- descriptive link text;
- accessible names for icon-only buttons;
- responsive layouts;
- support for browser zoom and text resizing;
- colour-contrast testing;
- text and icons used alongside colour-coded information;
- alternative text for informative images;
- empty alternative text for decorative images;
- light and dark modes;
- native Ghost membership and commenting features;
- accessible status messages for forms;
- reduced reliance on animation;
- a keyboard-accessible search dialog with a labelled search field;
- managed focus when search is opened and closed;
- keyboard navigation through search results;
- accessible search status and error messages;
- text labels identifying the access level of search results;
- keyboard-accessible dropdown menus with arrow-key, Home, End and Escape support;
- featured-story controls that can be used with a keyboard, with stories changing only when the visitor chooses;
- hidden featured stories are skipped when navigating with the keyboard;
- automated accessibility checks across representative page templates in light and dark modes and at desktop and mobile viewport sizes;
- manual keyboard and visual review of important site interactions;
- readable line lengths and spacing.
Automated accessibility checks can identify some problems but cannot establish complete compliance. Keyboard, screen-reader and visual testing remain necessary.
Keyboard access
The main site should be operable without a mouse.
Keyboard users should be able to:
- navigate the header and dropdown menus;
- open links and buttons;
- use forms;
- reach article content;
- open Ghost Portal;
- access comments;
- navigate the archive filters;
- open and close the site-search dialog;
- enter a search query;
- move through search results using the arrow keys;
- open a selected search result using Enter;
- close search using Escape and return focus to the control that opened it;
- reach footer and policy links.
The focused control should have a visible indication.
On desktop, the navigation parent links can also open dropdown menus. Press the Down Arrow or Space while a dropdown link has focus to open its menu. Use the Up and Down Arrow keys to move through its links, Home or End to move to the first or last link, and Escape to close the menu and return focus to the main link. Pressing Enter on the main link follows that link normally.
Site search
The site-search dialog is designed for keyboard and assistive-technology use.
When the dialog is opened, focus moves to the search field. Search results can be navigated using the Up and Down arrow keys, a selected result can be opened using Enter, and the dialog can be closed using Escape. When the dialog closes, focus returns to the control that opened it.
Search progress, result counts, empty results and errors are presented through accessible status messages.
Site search depends on JavaScript and the availability of Algolia. If search is unavailable, published material can still be reached through the Writing page, Archive, tags, navigation and direct links.
Text, zoom and reflow
The site is designed to work with browser zoom and text-size controls.
Content should reflow at common mobile widths and increased zoom without requiring horizontal scrolling, except where the nature of a particular item makes it unavoidable.
Images
Informative images should have alternative text describing their relevant content or purpose.
Decorative images can use empty alternative text so assistive technology ignores them.
Older posts or externally sourced images can contain incomplete alternative text. These will be improved when identified.
Colour and visual information
Important information should not depend only on colour.
Examples include:
- paid-content badges containing a lock icon and text;
- annotation styles using text labels, solid or dashed borders, background treatments and directional links as well as colour;
- current archive filters using an accessible current-page state;
- form errors displayed with text rather than colour alone.
Forms
Forms should include:
- programmatically associated labels;
- clear instructions;
- keyboard-accessible controls;
- visible focus indicators;
- readable error and success messages;
- appropriate input types and autocomplete attributes.
Third-party forms and payment interfaces are controlled by their providers.
Member, comment and payment interfaces
Membership, comments and subscription management are provided through Ghost.
Payments are provided through Stripe.
These services control parts of their own interfaces. Accessibility problems encountered in them can still be reported through the contact form so that assistance can be provided or the matter raised with the relevant provider.
External content
Pages can link to or contain third-party content.
External platforms can have accessibility limitations outside the direct control of Amanda Durkan Writes. Where practical, accessible alternatives or supporting context will be provided.
Known limitations
Known or possible limitations include:
- incomplete alternative text in some older material;
- third-party tools that do not fully meet accessibility standards;
- Ghost Portal, payment or comment interfaces controlled by external software;
- creative formatting that does not translate perfectly to every assistive technology;
- future changes to the Ghost accent colour or other theme settings could affect colour contrast and will require retesting;
- site search depends on JavaScript and a third-party search service and can be temporarily unavailable even when the rest of the site remains accessible;
- automated tools cannot fully inspect some Ghost Portal and commenting frames, so those interfaces require separate manual review;
- features not yet tested with every browser and screen-reader combination.
Issues will be prioritised according to their effect on readers and the resources available.
Reporting an accessibility problem
To report a problem, request an alternative format, or suggest an improvement, use the contact form and select Accessibility problem or request.
Useful information includes:
- the page address;
- what you were trying to do;
- what went wrong;
- the device and browser used;
- any assistive technology involved;
- the change or format that would help.
Accessibility reports will be reviewed and considered as part of ongoing improvements.
Alternative formats
Where reasonably possible, information can be provided in another accessible format on request.
What can be supplied and how long it takes will depend on the content and requested format.
Review
The statement will be reviewed as the site and its accessibility work develop.