Articles & Tutorials
Photographers15 min readBy PhotoView.io

Accessible Photo Galleries: A Photographer's Guide

How to build a photo gallery everyone can use: alt text, keyboard access, contrast, captions and a 15-minute test, plus what to look for in a platform.

Featured photograph for Accessible Photo Galleries: A Photographer's Guide

Accessible Photo Galleries: A Photographer’s Guide

Photographer testing a gallery with keyboard controls

An accessible photo gallery is one that a visitor can understand and operate without sight, without a mouse, or on a small phone screen. You get there with four things: a text description for every meaningful image, controls that work from the keyboard, readable contrast and captions, and a layout that holds up on mobile. Most of that is under your control as the photographer, and a portfolio platform that lets you update your work once and present it across your website, mobile and embeds keeps the effort from multiplying.

PhotoViewPresent Your Photography Across DevicesPhotoView helps you manage finished photos and videos in one dashboard, then publish them through responsive portfolio templates and mobile-ready presentations.Visit

TL;DR

  • Every meaningful photo needs a short, purposeful text description. Purely decorative images get an empty alt attribute.
  • A visitor must be able to open, move through and close your gallery with the keyboard alone, and always see where focus is.
  • Avoid auto-advancing slideshows. Give visitors control, readable captions and enough contrast, especially on phones.
  • For private businesses, courts evaluating ADA Title III lawsuits use WCAG 2.1 Level AA as the practical benchmark, so aim for it.
  • Automated scans find only part of the problems. Finish with a manual keyboard, zoom and screen reader pass.

Table of Contents

What “accessible” means for a photo gallery

A gallery is a collection of images, which sounds like the one format that text rules cannot touch. In practice it is the opposite. Accessibility work begins with finding keyboard obstacles and asking what the collection communicates to someone who cannot see the photographs. Alt text, captions and usable controls each answer a different part of that question.

Think of four groups of visitors:

  • Blind or low-vision visitors using a screen reader, software that reads page content aloud. They rely on your descriptions and on correctly labeled buttons.
  • Keyboard-only visitors, including people with motor impairments who cannot use a mouse or trackpad. They rely on the Tab key, Enter and Escape.
  • Visitors with low vision who zoom or enlarge text. They rely on contrast and layouts that do not break when text grows.
  • Everyone on a phone. Tiny pale captions, swipe-only navigation and hover effects fail them too.

The standard behind all of this is WCAG, the Web Content Accessibility Guidelines published by the W3C. You will see its numbered criteria (like 1.1.1 for text alternatives) throughout this guide, but you do not need to memorize them. The practical checks come first.

Write alt text that describes the photograph

Alt text is the short description stored in an image’s alt attribute. Screen readers read it aloud, and it also appears when an image fails to load. Section508.gov, the U.S. federal guide to accessible web design, says all non-text content needs a text alternative that serves the equivalent purpose. Its suggested test is simple: ask what text you would put there instead of the picture.

Rules that work for photography

Harvard’s Digital Accessibility Services gives guidance that fits a portfolio well. Keep alt text short, usually one or two sentences, focus on why the image was chosen rather than every detail, and skip “image of” or “picture of.” It also suggests names, locations or action words for photographs. The reason to drop “image of” is practical: screen readers already announce “image,” so the phrase gets read twice.

A few habits make this quick:

  1. Name the subject and the action. “A fisherman hauls a net onto a wooden boat at dawn, Hoi An.” beats “fishing.”
  2. Match the description to the context. A photographer writing for Envato Tuts+ shows that the same photo calls for a technical description in a tutorial and a business-oriented one on a portfolio site.
  3. Convey the mood, briefly. Guidance drawing on RNIB, the UK’s sight-loss charity, recommends focal point, context and details, with the emotion of the image carried through, and a warning not to write a novel.
  4. Make each image distinct. A gallery of twenty shots with the same filename or title as alt text tells a screen reader user nothing.
  5. Do not stuff keywords. Writing for search engines in a list of terms helps no one. If you want a deeper look at the search side, this guide to alt text for meaningful images covers purpose-based descriptions.

Decorative, linked and text images

The W3C’s images tutorial sorts alternatives by purpose. Informative images get a short description, decorative images get an empty alt attribute, images used as links or buttons describe the function, and images of text repeat the words in the image. For a photographer, that means a divider graphic gets alt=“”, while a thumbnail that links to a project should say where the click leads, not just what the thumbnail shows.

Four image types and their alternative text purposes

Captions and long descriptions

When a photo needs more than a sentence or two, move the detail into a caption or nearby text rather than cramming it into the alt attribute; ta11y suggests keeping alt text around 125 characters or fewer. Captions also help sighted visitors, which is why they are worth writing once and reusing. If writing them is the slow part, our AI caption workflow for photographers walks through it with ready-to-use prompts.

For fine art and documentary work, there is a case for going longer in the full-size viewer. Scout Burghardt of Cogapp argues that the image viewer is where a long description beats short alt text, because that is where sighted visitors zoom in and study detail.

Make the gallery work from the keyboard and with a screen reader

A gallery is interactive: thumbnails open a larger view, arrows move to the next image, a button closes it. Each of those has to work without a mouse. Section508.gov states that all functionality must be operable through a keyboard interface without specific keystroke timings, and that standard keyboard behavior should not be removed from native HTML elements.

What a good lightbox does

When an enlarged image opens as a dialog, the behavior should follow a predictable pattern. Focus moves inside the dialog and stays there while it is open, Escape closes it, and closing returns focus to the control that opened it. A common failure is focus wandering into the page behind the enlarged picture, which leaves a keyboard user lost.

Visitors also need to see where they are. The American Alliance of Museums asks for a clearly visible indication of the current point of regard, such as an outline around the focused item. That outline is the focus indicator, and it should never be switched off for looks.

Controls need names

Icon-only buttons (arrows, an X) are silent to a screen reader unless they carry a name. Media Gallery recommends names that describe the action, such as “Next image” or “Close image viewer”. Cogapp adds that an accessible label should match or begin with the visible label text, which helps people who control their device by voice.

If you work with a developer, one fix carries a lot of weight. A DEV Community audit guide argues that making the clickable image a real button or link rather than a div with a click handler gives you keyboard focus, Enter and Space activation and correct announcements. Our own developer checklist for image-first gallery templates goes through what to look for in a template.

Contrast, motion, video and mobile

Skip the auto-advancing slideshow

Auto-rotating carousels are the classic gallery trap. The W3C explains that screen reader users cannot perceive automatic rotation, so a slide can change mid-reading. The W3C’s carousel tutorial requires that users can pause movement, operate all item navigation by keyboard, and have changes communicated to screen readers.

The University of North Carolina’s web team goes further and notes that auto-rotating sliders harm everyone, since moving content is often mistaken for an ad and ignored. For a photographic collection, letting visitors advance the sequence themselves is usually the better design, and any auto-advance needs a straightforward pause control.

Contrast and captions

Level Access summarizes the WCAG 2.1 Level AA contrast minimums: 4.5:1 for normal text and 3:1 for large text, meaningful graphics and interactive elements. Two photography-specific traps:

Video in a mixed-media portfolio

If your portfolio mixes stills and video, video needs captions or a transcript. Johns Hopkins’ testing guide lists verifying video captions or transcripts as a standard check. Plan for it when you shoot behind-the-scenes or motion work.

Phones

Many visitors will see your work on a phone. Media Gallery notes that tiny pale-grey captions become hard to read on a phone, and enlarged text must not vanish behind fixed-height boxes. Check your gallery at browser zoom and larger text sizes. For the mobile side of portfolio design, see our 8-step phone test for mobile portfolio sites and our guide to fast mobile portfolios with srcset and AVIF.

Which standard applies to a photographer’s site

The U.S. rule that gets the headlines is the Department of Justice’s ADA Title II rule, which sets WCAG 2.1 Level AA for state and local government web content and apps. It covers government entities, not private photographers. An interim final rule published April 20, 2026 extended its compliance dates to April 26, 2027 for larger entities and April 26, 2028 for smaller ones, per the same ADA.gov guide.

For a commercial photography site, the picture is different. One 2026 compliance guide explains that the Title II rule never applied to commercial websites and no federal deadline exists for them, but courts evaluating ADA Title III lawsuits use the same WCAG 2.1 Level AA benchmark. That makes Level AA the sensible target.

WCAG 2.2 is worth knowing too. It is backward-compatible with 2.1 and adds six criteria covering mobile accessibility, dragging alternatives, focus visibility and accessible authentication. Meeting WCAG 2.2 also means meeting 2.1, and the W3C itself advises using WCAG 2.1 to maximize future applicability of your efforts. If you are bound by a client contract or a public-sector commission that names a standard, confirm the exact requirement with an attorney.

Test your gallery in 15 minutes

Automated checkers are a good first pass, not the whole job. The University of Chicago’s Center for Digital Accessibility says automated tools identify approximately 40% of issues, while about 60% need manual testing with a keyboard, screen reader and human judgment. Work through this order:

  1. Run an automated scan. Browser extensions such as WAVE or axe catch failing contrast ratios and missing ARIA attributes. Fix what they flag.
  2. Tab through the page. Press Tab forward and Shift+Tab back. You should always see a focus indicator, and focus order should follow the visual order.
  3. Open and close a photo. Press Enter on a thumbnail, move with the arrow controls, then press Escape. Focus should stay inside the viewer and return to the thumbnail afterward.
  4. Zoom. Johns Hopkins recommends zooming to 400% and checking for loss of content or functionality. The close button must stay reachable.
  5. Listen. Use VoiceOver on a Mac (Cmd+F5) or the free NVDA reader on Windows, and hear how each photo and button is announced. Media Gallery cautions to check what assistive technology actually announces rather than assuming labels are heard as intended.
  6. Repeat on a phone. Check captions, tap targets and navigation in the mobile view.

Media Gallery makes a useful point about feature lists: “keyboard support” on a spec sheet matters less than completing the actual journey through your own page. Do the journey on your published site, after your own photos, captions and branding are in place.

Where PhotoView fits

PhotoView is a portfolio platform built so you spend more time shooting and less time managing websites. You store and curate finished photos and videos in one dashboard, publish through 30+ responsive portfolio templates, and keep live website embeds current without rebuilding your content. All templates are included in every plan.

Where PhotoView fits

That structure suits the work above. You write descriptions and captions once as part of curating your work, then present the same collection across your website, mobile presentations and embeds. Multiple galleries and mixed media let you organize series the way a visitor would look for them, and our guide to organizing multiple photography galleries shows how. If you want a full-screen viewing experience that respects your framing, read about a full-screen photo gallery that keeps ratios.

Plans are tiered by storage, with all portfolio and website features included. As published on our site, Starter is $3.99 per month or $39.99 per year, Growth is $5.99 per month or $59.99 per year, Studio is $7.99 per month or $79.99 per year, and Premier is $11.99 per month or $119.99 per year. A Custom plan is available for high-volume storage. You can start with a free trial and run the 15-minute test above on your own published portfolio.

PhotoView

See the plans and start your trial at PhotoView.io. If you publish from Lightroom, the Lightroom portfolio page shows how that works, and if you already have a site, you can embed a live photography portfolio on it.

Our view: accessibility is part of presenting the work

Photographers spend years learning to control how an image is seen. An accessible gallery extends that care to the people who see it differently: through a screen reader, a keyboard, a zoomed browser or a small phone.

We built PhotoView around a simple idea: you should update your work once and have it presented well everywhere it is discovered, on your website, on mobile and in embeds. That is the same discipline accessibility asks for. Do the thoughtful work once, in one place, and let it carry.

So our advice is practical. Describe your photographs the way you would describe them to a client on the phone. Choose a portfolio-first layout where the image leads and the controls stay out of the way. Skip the auto-advancing slideshow. Then test the finished site with your keyboard before you share the link.

A clean, organized portfolio with 30+ responsive templates to choose from means you can match the layout to your style and still keep the experience simple for every visitor.

Mitch Russo

FAQ

Do I need alt text on every photo in my portfolio?

Every meaningful image needs a text alternative, and every image should carry an alt attribute. Section508.gov notes that decorative images take an empty alt=“”. For portfolio photos, write one or two distinct sentences about what each shot shows.

Is my photography website legally required to be accessible?

The ADA Title II rule covers state and local governments, not private photographers. For commercial sites, courts in Title III lawsuits use WCAG 2.1 Level AA as the benchmark, so it is the practical target. For a specific obligation, such as a contract with a public agency, ask an attorney.

Are slideshows and carousels a problem?

Auto-advancing ones are. Users must be able to pause movement and operate the controls by keyboard, and screen reader users cannot perceive automatic rotation. A gallery where visitors move from one image to the next themselves avoids the problem.

Can an automated checker tell me my gallery is accessible?

Not on its own. Automated tools find roughly 40% of issues, so pair a scan with a keyboard pass, a zoom check and a listen with a screen reader.

How long should alt text be?

Usually one or two sentences. Harvard advises focusing on why the image was chosen rather than every detail, and ta11y suggests around 125 characters or less, with longer detail placed in a caption.

Sources

Recommended