Accessibility
Niles Connect should be usable by as many people as possible.
Accessibility is part of the ongoing design and development of
Niles Connect. The site is being built to work across desktop,
tablet, and mobile devices and to support common accessibility needs.
Design goals
Accessibility should be built into the site.
Niles Connect aims to make its public information and community
tools understandable, navigable, and usable across a range of
devices and interaction methods.
Readable content
Text, headings, links, buttons, forms, and other interface elements
should use clear language, readable sizing, and sufficient contrast.
Keyboard navigation
Interactive controls should be usable without requiring a mouse
whenever the underlying site feature supports keyboard interaction.
Clear structure
Pages should use meaningful headings, sections, labels,
and navigation so information is easier to understand
and move through.
Visible focus
Links, buttons, forms, menus, and dialogs should provide
visible feedback when they receive keyboard focus.
Responsive layouts
Pages should adapt to smaller screens rather than forcing
desktop-sized layouts onto mobile visitors.
Useful alternative text
Meaningful images should use appropriate alternative text
when the image communicates information that is not already
conveyed by surrounding text.
Mobile access
Niles Connect is intended to work well on phones and tablets.
Many residents will access community information from a mobile device,
so responsive behavior is treated as a core part of the site rather
than an optional desktop-to-mobile conversion.
Touch-friendly controls
Buttons, navigation links, filters, and other interactive controls
should be reasonably sized for touch input.
No unnecessary horizontal scrolling
Standard site pages should reflow to fit smaller screens
without requiring visitors to pan across a desktop-width page.
Readable forms
Forms should stack appropriately and remain usable on smaller
screens without clipped fields or inaccessible controls.
Content accessibility
Accessible design also depends on the content itself.
Articles, community submissions, records, documents,
business listings, and other information may come from
different authors and source systems.
Headings should be meaningful
Page and article headings should describe the information
that follows rather than being used only for visual styling.
Links should make sense
Link text should provide useful context whenever practical
instead of relying only on vague phrases such as “click here.”
Images should support the content
Images should not be the only way important information
is communicated when a text equivalent can reasonably be provided.
Documents may vary
Public records and externally supplied documents may not always
have been created in an accessible format by their original source.
Community content varies
User-submitted content may not always follow the same accessibility
standards as site-authored pages.
Plain language helps
Site instructions and navigation should use direct,
understandable language whenever practical.
Interactive tools
Complex tools may require additional accessibility work.
Maps, filters, dashboards, resident connections, forms,
document viewers, and other interactive components can present
accessibility challenges beyond ordinary page content.
Forms
Form fields should have understandable labels,
usable error messages, and predictable keyboard behavior.
Maps
Interactive maps may not provide the same experience
for every visitor, so important information should be made
available through accompanying text or data where practical.
Dialogs & notices
Popups and dialogs should support keyboard interaction,
visible focus, and a clear method of dismissal.
Current limitations
The site is still being developed and tested.
Niles Connect is an ongoing project. Some pages, plugins,
imported documents, forms, maps, or other components may still
contain accessibility problems that have not yet been identified
or corrected.
Third-party content
External websites, embedded services, source documents,
and imported material are not always controlled by Niles Connect.
Legacy components
Older plugin or page components may require additional work
as the site continues moving toward the shared design system.
Testing continues
Desktop, tablet, phone, keyboard, contrast, form,
and other accessibility testing should continue
as features are rebuilt.
Report a barrier
Tell us when something is difficult or impossible to use.
Accessibility feedback is useful during development.
When reporting a problem, include the page, device,
browser, and what you were trying to do if possible.
soxside@gmail.com
Use a subject such as “Accessibility Issue” and describe
the specific problem you encountered.
Helpful details
What to include in an accessibility report
Page or feature
Include the page address or describe the part of Niles Connect
where you encountered the problem.
Device & browser
Tell us whether you were using a phone, tablet, or computer
and which browser you were using if known.
What happened
Explain what you expected to do and what prevented you
from completing the task.
Accessibility is an ongoing effort.
This page describes the site’s accessibility goals and development
approach. It should not be interpreted as a claim that every page,
plugin, document, or feature currently meets every accessibility
standard or guideline.
More information
Need help using Niles Connect?
How It Works explains the major site areas, and the Contact page
provides the general email address for site questions and feedback.