// legal — accessibility statement

Accessible by structure,
not by afterthought

Arlo is committed to building and maintaining systems that are accessible, usable, and inclusive across a wide range of users, devices, and assistive technologies.

Accessibility is a core consideration in the design and development of modern web systems — addressed across structure, design, and content.

// applied layers

Four layers, addressed in parallel.

~/accessibility/layers.conf

structuresemantic html · landmarks · heading order
visualcontrast · typography · interactive states
keyboardfull operability · tab order · visible focus
mediaalt text · captions · accessible forms

Standards alignment

Our work is aligned with widely accepted accessibility standards, including:

01Web Content Accessibility Guidelines (WCAG) 2.1
02Applicable regional or organizational accessibility requirements

Specific compliance levels (e.g., AA) are defined based on project requirements.

Accessibility approach

Accessibility is addressed across multiple layers:

Structure & semantics

·Proper use of HTML structure and landmarks
·Logical heading hierarchy
·Accessible navigation patterns

Visual & interaction design

·Sufficient color contrast
·Readable typography
·Clear interactive states (focus, hover, active)

Keyboard & navigation

·Full keyboard accessibility
·Logical tab order
·Visible focus indicators

Media & content

·Alternative text for images
·Captioning and transcripts where applicable
·Accessible form labeling and error handling

Testing & validation

Accessibility is validated through a combination of:

01Automated testing tools
02Manual review
03Real-world usage considerations

Accessibility considerations are incorporated into QA processes alongside performance and functionality — not limited to final review.

Ongoing maintenance

Accessibility is not a one-time implementation. Systems are designed to support ongoing compliance as content and functionality evolve.

We support:

01Accessibility reviews post-launch
02Iterative improvements
03Guidance for maintaining accessible content

Limitations

While we strive to meet accessibility standards, certain limitations may arise due to:

01Third-party integrations
02Client-provided content
03Platform or system constraints

These are identified and addressed where possible.

Collaboration

Accessibility outcomes are strongest when addressed collaboratively.

Strategic planning, content structure, and user experience considerations may be supported in collaboration with Jirehnet.

Feedback

We welcome feedback regarding accessibility.

If you encounter accessibility barriers or have suggestions:

hello@arlo.eng

Continuous improvement

Accessibility practices evolve alongside standards and technologies. Arlo continuously refines its processes to improve accessibility outcomes across projects.