Buildrok is committed to ensuring digital accessibility for people with disabilities. We are continually working to improve the accessibility of our website and services so that everyone can use them effectively, regardless of ability or assistive technology.

Our accessibility goal

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA as our target standard. These guidelines explain how to make web content more accessible to people with disabilities, including visual, auditory, physical, speech, cognitive, and neurological disabilities.

Measures we have taken

We have implemented the following accessibility features and practices on buildrok.com:

Skip navigation link: a "Skip to main content" link appears at the top of every page when keyboard users press Tab, allowing them to bypass the navigation menu.
Semantic HTML: pages use appropriate HTML elements including headings (h1–h3), landmark regions (header, nav, main, footer), and lists to provide meaningful structure.
Keyboard navigation: all interactive elements (links, buttons, form fields, menus) are reachable and operable via keyboard alone. The navigation dropdown and mobile menu close when Escape is pressed.
Visible focus indicators: keyboard focus is visually indicated on interactive elements.
Form labels: all form fields have associated visible labels. Required fields are marked with aria-required="true".
Error announcements: form error messages use role="alert" and aria-live="assertive" so screen readers announce errors when they appear.
ARIA attributes: menus and interactive widgets include appropriate ARIA roles and states such as aria-expanded, aria-haspopup, aria-label, and aria-pressed.
Decorative images: decorative SVG icons are marked with aria-hidden="true" so screen readers do not announce them.
Dark mode support: users can toggle between light and dark color schemes for improved readability based on their preference. The theme preference is remembered across visits.
Responsive design: the site reflows for different screen sizes and zoom levels.
Color contrast: we aim to maintain sufficient color contrast ratios for text and interactive elements in accordance with WCAG 2.2 AA requirements (4.5:1 for normal text; 3:1 for large text and UI components).
Language attribute: the page language is declared as English (lang="en") on every page.
External link disclosure: links that open in a new tab or window are labeled to indicate this behavior.
FAQ accordion: the FAQ uses native HTML <details>/<summary> elements, which are natively accessible to screen readers and keyboard users.

Known limitations

Despite our efforts, some areas of the site may not yet fully conform to WCAG 2.2 AA. Known or potential limitations include:

App dashboard pages (accessible after login) use JavaScript-injected content for performance reasons. These pages are undergoing ongoing accessibility review.
Customer-published websites (the websites created and published by Buildrok users) are controlled by those users. The accessibility of those sites depends on the content and customizations made by each user. Buildrok is not responsible for the accessibility of content on customer-published sites.
Third-party integrations: some flows (such as Google OAuth sign-in) involve third-party pages or widgets that are outside our control.

Feedback and contact

We welcome your feedback on the accessibility of buildrok.com. If you experience any barriers to access, or if you need content in a different format, please let us know:

Email: support@buildrok.com
Contact form: buildrok.com/contact

We aim to respond to accessibility feedback within two business days. We take all reports seriously and will work to address legitimate accessibility barriers as quickly as practicable.

Formal complaint process

If you are not satisfied with our response, you may contact the U.S. Department of Justice — ADA.gov or your applicable disability rights authority.

Technical specifications

Accessibility of buildrok.com relies on the following technologies to conform to WCAG 2.2: HTML5, CSS (Tailwind CSS), and JavaScript. These technologies are relied upon for conformance.

We test our pages using keyboard-only navigation, screen reader spot-checks (including VoiceOver on macOS), browser developer tools, and automated checks via Lighthouse and axe.