Accessibility
If your company has its headquarters or a commercial representative in Brazil, its website must be accessible to people with disabilities: that is what article 63 of Brazil's Inclusion Law (Lei Brasileira de Inclusão, Law 13,146/2015) requires. Since March 2025, the Brazilian standard ABNT NBR 17225 spells out what that means in practice, with requirements aligned with WCAG 2.2 level AA. The guides below explain the law, the criteria that come up most in audits and how to test your site.
LBI and NBR 17225: what Brazilian law requires of a website
Article 63 of Brazil's LBI requires accessible websites from companies based or represented in Brazil. What NBR 17225 asks and how to check common failures.
Go deeper
- Accessibility
WCAG 2.2 level AA: what changed and how to check it
WCAG 2.2 added nine new criteria and removed 4.1.1. Which ones count for level AA, how to test each one and how they map to Brazil's NBR 17225.
- Accessibility
Do accessibility overlays meet the law?
Accessibility widgets and overlays do not make a site conform to WCAG or Brazil's NBR 17225. What they do, their limits and what actually fixes a site.
- Accessibility
Accessible forms: labels, errors and keyboard
Associated labels, errors described in text, keyboard, visible focus and autocomplete: what WCAG 2.2 asks of a form, with HTML examples.
- Accessibility
Color contrast: how to meet WCAG criteria 1.4.3 and 1.4.11
Text needs 4.5:1; large text and UI components need 3:1. What counts as large text, how to calculate contrast, the exceptions and how to test.
Frequently asked questions
- Does the LBI apply to every website?
- Article 63 applies to websites maintained by companies with headquarters or commercial representation in Brazil and to government websites. The law has no technical checklist of its own: it says to follow internationally adopted accessibility guidelines, which are the W3C's WCAG.
- What is the difference between NBR 17225 and WCAG?
- WCAG is the W3C's international guideline. ABNT NBR 17225, published in March 2025, adopts WCAG 2.2 and organizes it into 96 requirements and 50 recommendations. Meeting every requirement of the standard is equivalent to WCAG 2.2 levels A and AA.
- Can an automated tool tell whether a site is accessible?
- Not on its own. The W3C says automated tools help with evaluation, but some criteria depend on manual testing, such as navigating with the keyboard only and using a screen reader.
- Does an accessibility plugin or widget meet the legal requirement?
- No W3C standard, and not NBR 17225 either, recognizes an overlay as a way to meet the criteria. Conformance depends on fixing the site's code and testing.
Other topics
Privacy
Brazil's LGPD (Lei Geral de Proteção de Dados, Law No. 13,709/2018) never mentions cookies, but it applies to any cookie, pixel or script that collects personal data from site visitors.
3 guidesPerformance
Core Web Vitals are three Google metrics that measure the real experience of visitors: LCP measures loading, INP measures responsiveness to clicks and taps, and CLS measures visual stability.
6 guidesSecurity
The first security step on a public website is to check what any visitor can see from the outside: whether every request goes to HTTPS with a valid certificate, whether the security headers are present, whether any files are exposed, whether the CMS and plugins are up to date and which third-party scripts run on the page.
3 guidesTechnical SEO
Google shows a page only after crawling it, processing the content and deciding to store it in the index.
5 guides
Partners
Partner benefits with one coupon.
WPLIGHT20% OFFGet the offer from WP Rocket (opens in a new tab)
25% OFFGet the offer from Perfmatters (opens in a new tab)
Partner links. We may earn a commission at no extra cost to you.