city_hall

Official websites use .boston.gov

A .boston.gov website belongs to an official government organization in the City of Boston.

lock

Secure .gov websites use HTTPS

A lock or https:// means you've safely connected to the .gov website. Share sensitive information only on official, secure websites.

Heat Emergency in Boston
/
Mayor Wu announced a heat emergency in the City of Boston through Wednesday, July 17. Cooling centers will be open at 14 BCYF community centers Monday through Wednesday, from 9 a.m. - 5 p.m.

Building a Boston.gov that is accessible for all

By working with a local partner, we’re keeping ourselves honest when it comes to accessibility.

We’ve mentioned this before, but our work on Boston.gov is never done. Thanks to an ongoing partnership with a small, local business, Iterators LLC, we have conducted the City’s first-known Voluntary Product Accessibility Template (VPAT). This point-in-time report uses four modes of accessibility (perceivable, operable, understandable, and robust) and 61 testable success criteria. These metrics verify online and digital accessibility efforts completed by the City to-date, and document future work that should be done.

You can find a complete copy of the report online, but we’re sharing some highlights.


Accessibility snapshot

We’re happy to report that the City’s website maintains a AA standard. But, throughout this project, it was clear that software cannot replace the quality of human review. When the first review was done, we found out that we only partially met the full list of criteria. About 50 of the 61 testable success criteria were either partially or fully met, but this gave us clarity on what to do next.

So far, we’ve focused on enhancing:

Color contrast:

We made some tweaks to our colors a while back for better color contrast and increased readability. We realized through this project that these updates weren’t quite reflected across the entire site. Now they are.

Html parsing

Parsing issues often lead to errors with page layout and wrong html tags. We want to focus on getting this right, so that assistive devices like screen readers can accurately navigate Boston.gov. We’ve started this work on some portions of our site, but have more work to do.

Keyboard navigation

We want to ensure that all links and buttons have titles, alternative (alt) tags, and names.

We plan to make sure tables, lists, and iFrames on the site have captions, titles, and summaries. We will also be adding labels to input fields, such as form fields. These enhancements will make the online experience better for everyone, but particularly for those who use assistive devices, like screen readers.

Images:

We’ve changed many icons from being “background images” to being images recognized by all devices. By making this change, folks who use screen readers and similar devices are able to more easily access the “alt” text of our icons to give them more context on Boston.gov. 

What’s next? Better headings and labels

Making sure everything has appropriate html markup is a start. But, we have more work to do to ensure that all those labels have meaningful content and a set hierarchy on the page. This work is ongoing.


Creating accessible experiences outside of Boston.gov

While this isn’t a part of our recent VPAT report, we think it’s important to highlight some of the accessibility work we’ve been adding to our other digital tools, specifically social media. Among our responsibilities, we manage the City of Boston’s main social media accounts, and even in this medium, accessibility is key. When displaying text in graphics in our posts, we either add “alt text” for those graphics, or we make sure the text in the actual post is the same as the text in the graphic. We also post multilingual graphics and text when we have that information available, especially during major events like the 2020 Election and the COVID-19 pandemic. 

Easier access to audio and video

When creating videos for sharing on YouTube and other social media platforms, we prioritize including caption files. Our YouTube videos also provide transcripts and contextual video descriptions, whenever possible. For Instagram, where a separate caption file isn’t possible, we often add the captions directly into our videos. We do this by adding burned-in subtitles (they appear as part of the video file itself). When critical and available, we also create multilingual videos in the City of Boston’s top languages.


Any questions or feedback? Send us an email at digital@boston.gov. We’re also in constant partnership and communication with our colleagues at the Disabilities Commission and the Office of Language and Communication Access. If you write to them about your experiences on Boston.gov or with any of our digital tools, they will also make sure to share your feedback with us.

If you want to learn more, check out some other posts about our work in creating an accessible City of Boston:

  • Last updated:
  • View the report

    You can download the complete Voluntary Product Accessibility (VPAT) report:

    Download VPAT report

    • Last updated:
  • View the report

    You can download the complete Voluntary Product Accessibility (VPAT) report:

    Download VPAT report

  • Back to top
https://www.boston.gov/news/building-bostongov-accessible-all
www.boston.gov
CC-MAIN-2024-30
54632
application/http; msgtype=response
sha1:GZIB4BHSW2OEQRPU5RFIYXHXYRTJ5XI3
<urn:uuid:3524a83c-4549-4306-b415-7e03da939f58>
2024-07-17T19:45:58Z
107.154.103.58
text/html
sha1:SJVRTBUYS4EYO6CEOXDPT6B7ACONNNUI
<urn:uuid:69468953-30a1-4f4a-95b0-47a9e7c2d973>
https://www.boston.gov/news/building-bostongov-accessible-all
response
<urn:uuid:c4fdc238-3992-40d0-be30-7184f31438a9>
isPartOf: CC-MAIN-2024-30
publisher: Common Crawl
description: Wide crawl of the web for July 2024
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-148
software: Apache Nutch 1.20 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.5-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/