This page provides the recommended accessible elements that meet the Web Content Accessibility Guidelines (WCAG 2.0) along with the Section 508 standards. The Hill College website exceeds the accessible benchmarks and will continue to improve and sustain this initiative. The Hill College vision and goal is making our site accessible to all faculty, students, staff and visitors.


Web Accessibility for Designers Infographic

Web Accessibility for Designers infographic with link to text version at WebAIM.org

How To use the Source Code Tool

The Advanced Code Editor (ACE) is Cascade CMS' built-in syntax-highlighting editor. Assets that are editable with the code editor include Files, Template, Formats, and Text/XML Blocks. The editor provides syntax-highlighting for a variety of languages, auto-indentation and auto-formatting, code folding and code snippets. For our purpose, ACE will be referenced as Source Code Tool. Please review the Using Source Code Tool PDF prior to coping and pasting code to your pages.

Buttons

Copy & Paste code:

<div style="text-align: center;"><a class="slide-button alt" href="https://www.hillcollege.edu">HC Theme Button</a></div>

All that will need to be done is to edit the URL or path ("href" is where the URL and/or path to the file will be added. everything inside the quotes is where you plug in the url or path, don't delete the quotes) and text on the button.

*Please submit a ticket to Phillip Esparza or Eric Larson to have the call to action button added.

 


Accessible PDF

A document or application is considered accessible if meets certain technical criteria and can be used by people with disabilities. This includes access by people who are mobility impaired, blind, low vision, deaf, hard of hearing, or who have cognitive impairments. The PDF is an accessible sample. All PDFs need to be accessible prior to publishing online.

Note: These Best Practices techniques require access to Adobe Acrobat Pro DC. Adobe Acrobat Reader DC and Adobe Acrobat Standard DC do not have the complete set of tools needed to create and validate PDF documents for accessibility.


Accessible Tables

This table is a responsive, bordered, and accessible example.

Testing Center Contacts
First Name Last Name Hero Title
Bruce Wayne Batman
Peter Parker Spiderman
Bruce Banner The Hulk
Clark Kent Superman
<div class="table-responsive-md">
<table class="table table-bordered"><caption><strong>Testing Center Contacts</strong></caption>
<thead class="thead-dark">
<tr>
<th scope="col">First Name</th>
<th scope="col">Last Name</th>
<th scope="col">Hero Title</th>
</tr>
</thead>
<tbody>
<tr>
<td>Bruce</td>
<td>Wayne</td>
<td>Batman</td>
</tr>
<tr>
<td>Peter</td>
<td>Parker</td>
<td>Spiderman</td>
</tr>
<tr>
<td>Bruce</td>
<td>Banner</td>
<td>The Hulk</td>
</tr>
<tr>
<td>Clark</td>
<td>Kent</td>
<td>Superman</td>
</tr>
</tbody>
</table>
</div>

This is a Hoverable Row table. Table is designed to be responsive, hover state on rows, accessible attributes and with a colspan attribute.

List of youth football teams
# Team Town Division
1 Sharks Austin Central
2 Dust Devils San Antonio South
3 Stars Dallas North
Games will start at 9:00am.
<table class="table table-hover"><caption>List of youth football teams</caption>
<thead>
<tr>
<th scope="col">#</th>
<th scope="col">Team</th>
<th scope="col">Town</th>
<th scope="col">Division</th>
</tr>
</thead>
<tbody>
<tr>
<th scope="row">1</th>
<td>Sharks</td>
<td>Austin</td>
<td>Central</td>
</tr>
<tr>
<th scope="row">2</th>
<td>Dust Devils</td>
<td>San Antonio</td>
<td>South</td>
</tr>
<tr>
<th scope="row">3</th>
<td>Stars</td>
<td>Dallas</td>
<td>North</td>
</tr>
<tr>
<td colspan="4">Games will start at 9:00am.</td>
</tr>
</tbody>
</table>

Image

Decorative Image Sample

The "alt" tag is empty, Code:

<img alt="" caption="false" class="" src="" width="500" height="357" />

For a decorative Image, select "decorative image" before clicking "OK" on the edit image dialog screen. See below:

Edit image dialog box with decorative image selected

Images used to supplement other information

The above image is a supplement for the content of the page, notice that the "alt" tag has a description of the image, below:

<img alt="Edit image dialog box with decorative image selected" caption="false" class="" src="" width="331" height="279" />

 

Icon image that has a function (hyperlinked)

Print this page
Use the functionality of the link or button icon as your "alt" text alternative when working with icon images, Code:

<img alt="Print this page" caption="false" src="" width="144" height="144" />
More information on Alternative Text can be found on the WebAIM website.

Links

Links or Hyperlinks must be either Bold or Underlined:

jspicer@sample.com or jspicer@sample.com

Refrain from using "click here",

Avoid This: "please click here" - here being the link.

Practice This: "Please click about transcripts for more information" - Use informative link phrases.

In some cases it may make sense to precede a link phrase with "more" or "read more about," (e.g. "more about college scholarships"), but if these extra words can be avoided, it is probably best to avoid them (e.g. "college scholarships" may convey the same meaning as "more about college scholarships," depending on the context). 

Links should be limited to 60:

  • It's recommended that no more then 60 links be added to internal pages.
The same link text is used for links going to different destinations in the Navigation. Users might not know the difference if they are not somehow explained. If the destination page is the same, this is not an issue. If the destination pages are not the same, make sure the links can be distinguished by their link texts or WAI-ARIA labels ('aria-labelledby' or 'aria-label') alone to make the difference clear to all users:

 Example:

"Admissions" In the nav-bar on top of pages should point to the same location as the "Admissions" listed in the side-nav.

Challenges for users when using web addresses and URLs are readability and length.

URLs are not always human-readable or screen-reader friendly. Many URLs contain combinations of numbers, letters, ampersands, dashes, underscores, and other characters that make sense to scripts and databases but which make little or no sense to the average person. In most cases, it is better to use human-readable text instead of the URL. The human readable link Building Accessible Websites is more user-friendly than the link to purchase the book by the same title on Amazon.com, which consists of a 108-character link full of numbers, slashes, and text that is not very human-readable. (http://www.amazon.com/Maximum-Accessibility-Making-Usable-Everyone/dp/0201774224/ref=sr_1_13?keywords=Accessible+Web+Sites&qid=1563888961&s=books&sr=1-13)

Does this mean that URLs should never be used as links? No. If the URL is relatively short (such as a site's homepage), the URL may be used as the link text. The key is to be considerate of screen reader users who must listen to the longer, less intelligible URLs.

 


Accessibility Contact

If you have any questions regarding accessibility and/or any of the defined elements above, please contact:

Phillip Esparza
Web Administrator
254.659.7846
Email Contact