Screen meeting AA criteria
The development arm builds the screen checking contrast, target size, visible focus and field labels, on the task branch.
Deliverable: screen on the branch, ready for reviewOcto for front end and accessibility · dev and reviewer arms
A finished screen is a screen everyone can use.
WCAG 2.2 is a W3C Recommendation and the ISO/IEC 40500:2025 standard. In Brazil, the Brazilian Inclusion Law makes accessibility mandatory on the websites of companies headquartered or represented in the country. Two Octo arms work at this step: development builds the screen with the AA criteria checked, and the reviewer tests it on desktop and mobile through the real path. Sign-off on the screen belongs to the tech lead.
ArmsDev and reviewerwork at this step
WCAG 2.2ISO/IEC 40500:2025W3C Recommendation
Sources6listed at the end of the page
01
What Octo does on the screen.
Four possible deliverables. The layout and sign-off on the screen belong to the tech lead and the interface designer.
Desktop and mobile testing
The reviewer opens the screen through the real path, at desktop and mobile widths, and checks the content, not just the absence of errors.
Deliverable: screen report at both widthsFailures by criterion
Whatever falls short becomes a list with the matching WCAG criterion, such as minimum contrast or target size, for the team to prioritize.
Deliverable: list of failures by criterionARIA only when it helps
The code uses semantic HTML before turning to ARIA, because bad ARIA hurts screen reader users.
Deliverable: reviewed markup
02
Eight arms, one screen.
The same Octo cycle, applied to this step. Each arm has a narrow role; your company's tech lead is in charge and approves.
-
Discovery
Reads the current front end
Framework, components, stylesheets and how the screens are put together today.
-
Data
Connects the screen to the data
Where each field comes from, so the screen doesn't show what the role isn't allowed to see.
-
Security
Checks what the screen exposes
Sensitive fields, error messages and what each role can see.
-
Architecture
Plans the screen
Components, states and the AA criteria the delivery must meet.
-
Development
Builds the screen
Semantic HTML, with contrast, target, focus and labels checked.
-
Review
Tests at both widths
Desktop and mobile, through the real path and with the least-privileged role.
-
Release
Publishes with your OK
The screen only goes to production with the approval of whoever is in charge.
-
Documentation
Records the criteria
Which criteria were checked and what is still pending.
Octo does not declare conformance. Approving the layout, deciding which conformance level to claim and signing any accessibility statement are up to your team; testing with people with disabilities is not done by Octo.
03
Some of the criteria Octo checks.
WCAG 2.2 criteria checked on the screen. The W3C Recommendation remains the reference.
| Criterion | What it requires | Basis |
|---|---|---|
| 1.4.3 Contrast (Minimum) (AA) | 4.5:1 for text; 3:1 for large text | W3C, Understanding WCAG 2.2 |
| 2.5.8 Target Size (Minimum) (AA) | At least 24 by 24 CSS pixels, with exceptions | W3C, WCAG 2.2 |
| 2.4.11 Focus Not Obscured (Minimum) (AA) | The focused component is not entirely hidden by author-created content | W3C, WCAG 2.2 |
| 3.3.8 Accessible Authentication (Minimum) | No step requires a cognitive function test, such as remembering a password or solving a puzzle | W3C, WCAG 2.2 |
04
From request to routine.
Three steps. Each one only makes sense once the previous one has shown results on your team.
A proposal, not a promise
New screens at AA
New screens ship with the AA criteria already checked.
- Contrast, target, focus and labels
- Desktop and mobile testing
Existing screens
The reviewer goes through the existing screens and lists the failures by criterion.
- List prioritized by criterion
- Fixes in small tasks
Checked on every delivery
Every screen task ends with a check at both widths.
- Screen report with every delivery
- Criteria recorded in the dossier
05
Confirmed by source.
Each point below has a source published by the organization responsible for the standard, the specification or the tool, or in Brazilian federal law. The sources are in the next section.
8
points with a published source, each with its reference alongside.
- ConfirmedWCAG 2.2
- WCAG 2.2 is a W3C Recommendation; the current version is dated December 12, 2024.Source: W3C, WCAG 2.2
- ConfirmedPrinciples and levels
- WCAG is organized into four principles (perceivable, operable, understandable and robust) and three conformance levels: A, AA and AAA.Source: W3C, WCAG 2.2
- ConfirmedTarget size
- Criterion 2.5.8, new in 2.2 and at level AA, requires touch or click targets to be at least 24 by 24 CSS pixels, with exceptions.Source: W3C, WCAG 2.2
- ConfirmedMinimum contrast
- Criterion 1.4.3 (AA) requires a contrast ratio of at least 4.5:1; large text, at least 3:1.Source: W3C, Understanding WCAG 2.2, contrast (minimum)
- ConfirmedISO standard
- WCAG 2.2 is an approved ISO standard, ISO/IEC 40500:2025. The W3C recommends using the newest version; versions 2.0, 2.1 and 2.2 are compatible with each other.Source: W3C, WCAG Overview
- ConfirmedBrazilian Inclusion Law
- Accessibility is mandatory on websites maintained by companies headquartered or commercially represented in Brazil.Source: Planalto, Law 13.146/2015, art. 63
- ConfirmedeMAG
- eMAG 3.1, from April 2014 and based on WCAG 2.0, is mandatory on Brazilian government websites and portals.Source: Governo Digital, accessibility model
- ConfirmedARIA
- The W3C ARIA authoring practices guide warns that no ARIA is better than bad ARIA.Source: W3C, ARIA Authoring Practices
06
What Octo does and what stays with you.
Octo prepares everything, but does not sign. The document of record stays with whoever is accountable for it.
Octo prepares
Maps, plans, codes on the task branch, reviews with evidence and prepares the release: plans, code, reviews, security reports and the system dossier.
Deliverable: material ready for reviewYour team reviews
Whoever is in charge is the company's tech lead or senior developer: they approve the plan, review the PR and merge it. Nothing goes to production without their approval.
Step: approval by whoever is in chargeWho signs and is accountable
Octo does not sign and is not accountable for the system. The tech lead accepts the risk and is accountable for the system in production; a security report or opinion is signed by a professional at the company.
Accountable: the company's tech lead
07
Sources.
W3C, federal legislation published on the Planalto website and Governo Digital. Accessed October 31, 2026.
- W3C: WCAG 2.2Principles, levels and criteria 2.5.8, 2.4.11 and 3.3.8
- W3C: Understanding WCAG 2.2, contrast (minimum)Criterion 1.4.3
- W3C: WCAG OverviewISO/IEC 40500:2025 and compatibility between versions
- Planalto: Law 13.146/2015 (LBI)Art. 63
- Governo Digital: eMAGThe federal government's accessibility model
- W3C: ARIA Authoring PracticesRead me first
Screens that everyone can use.
The assessment starts with the screens you already have, without changing anything. You get the list of what fails by criterion and decide with it in hand.