Our accessibility commitment
Georgia Raw targets WCAG 2.2 Level AA practices as a product and editorial baseline. Accessibility is part of design, engineering, publishing, corrections, and quality review—not a one-time certification.
We prioritize the mobile reading experience while supporting keyboard access, screen readers, browser zoom, text reflow, reduced motion, and a range of modern browsers and assistive technologies.
What we build and review
- Semantic landmarks, logical heading order, descriptive page titles, and meaningful link text.
- Full keyboard operation, visible focus, predictable navigation, and no keyboard traps.
- Readable type, sufficient color contrast, responsive reflow, and no color-only instructions.
- Labels, instructions, error summaries, and status announcements for future interactive controls.
- Alternative text, captions, credits, transcripts, and accessible descriptions appropriate to each media type.
- Reserved dimensions for media and advertising to reduce disruptive layout movement.
- Reduced-motion support and avoidance of flashing or unnecessarily animated presentation.
Accessible journalism
Access applies to the reporting itself. Headlines should be direct, abbreviations explained, timelines understandable, source links descriptive, and updates easy to find. Charts, maps, social embeds, video, audio, and breaking-news treatments need an equivalent way to understand the essential information.
Advertisements must remain distinguishable from editorial work and away from sensitive requests and controls. Accessibility-critical information cannot depend on an advertisement or third-party embed.
Testing and improvement
Automated checks help catch regressions, but they do not replace human evaluation. Important flows should also be reviewed with a keyboard, zoom and reflow, focus visibility, accessible names, landmark navigation, and representative screen-reader behavior.
New features are expected to preserve accessibility. Confirmed barriers are prioritized by severity, reach, and whether they block access to time-sensitive information.
Prepare a useful barrier report
Step 1
Identify the page
Save the page URL, visible heading, and the part of the page where the barrier occurs.
Step 2
Describe the task
Note what you were trying to read or do and what prevented completion.
Step 3
Record the environment
List the device, browser, input method, and assistive technology if you are comfortable doing so.
Step 4
Suggest an alternative
If known, explain what format or behavior would make the information usable. Do not include unrelated private data.