Skip to main content

Public reports › School districts · Texas

School district · Texas · 3,100 students

Fredericksburg ISD

fisd.org · homepage scanned Oct 15, 2026 · WCAG 2.2 A/AA automated check

C

Accessibility score

74/100 · Needs work

The homepage has issues that make common tasks harder for people using screen readers, keyboards or magnification. They are typically template-level and fixable in a day of vendor time.

1

Critical

2

Major

0

Minor

Screenshot of the Fredericksburg ISD homepage at scan time

Homepage as loaded by our crawler on Oct 15, 2026.

In plain English

What this means for visitors

The scan found some issues that may cause problems for visitors with disabilities, such as screen reader users who rely on buttons being clearly labeled. To improve accessibility, start by giving buttons descriptive names and adding titles to embedded frames. This will help ensure equal access to information for all visitors, as required by ADA Title II. Automated scans like this one catch many issues, but not all, so further review is recommended.

Findings

3 issue types found on the homepage

Each item is one failing rule; the count shows how many elements on the page trigger it. Severity follows axe-core impact levels.

#1CriticalWCAG 4.1.21 elementRule details ↗

Buttons have no accessible name

Icon-only buttons (search, menu, close) are announced as 'button' with no purpose.

Who it affects

Blocks a task outright for some visitors (for example an image-only flyer with no text, or a form field with no label).

First fix

Add an aria-label to icon buttons (for example aria-label="Open menu").

#2MajorWCAG 4.1.21 elementRule details ↗

Hidden content can receive focus

Keyboard users land on elements that screen readers say don't exist.

Who it affects

Makes a task significantly harder (low contrast, links with no name, missing frame titles).

First fix

Remove tabindex from hidden elements or don't hide focusable content with aria-hidden.

#3MajorWCAG 4.1.21 elementRule details ↗

Embedded frames have no title

Embedded maps, calendars and videos are announced as 'frame' with no description.

Who it affects

Makes a task significantly harder (low contrast, links with no name, missing frame titles).

First fix

Add a title attribute to each <iframe> (for example title="Google Map of the district office").

Severity guide

How to read the counts

Critical

Blocks a task outright for some visitors (for example an image-only flyer with no text, or a form field with no label).

Major

Makes a task significantly harder (low contrast, links with no name, missing frame titles).

Minor

Reduces clarity or consistency (heading order, landmarks, touch-target size).

What this grade does and does not cover

  • Covers: the public homepage only, loaded once in a desktop browser, tested with axe-core against WCAG 2.2 Level A and AA rules (a superset of the WCAG 2.1 AA standard in the DOJ rule).
  • Does not cover: inner pages, PDFs and documents, logged-in portals, video captions, alt-text quality, keyboard usability of custom widgets, or anything that needs a human judgment.
  • A grade is a monitoring signal, not a legal assessment or certification. How we score.