Accessibility Policy
Burton College takes Accessibility issues very seriously.
Shown below are the measures we've taken to meet the W3C Accessibility checklist.
| Accessibility Priorities | How Priority Met |
| Priority 1 (Level A): | |
| When using any pictures, include an Alternative Description Tag (Alt Tag) so that a user with a visual disability will know what is supposed to be visible in the relevant area of the screen. | We use ALT and LONGDSC tags fully |
| Avoid the use of colours that may create problems for individuals with colour-blindness or for those using older monitors incapable of displaying more than 256 colours. | We use web-safe colours or colours that will degrade acceptably on older monitors, and we take colourblindness into account when using colourschemes. All body content text is black on a white background. |
| Each page must have the following line as its first line of html code: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"> |
Each page has this |
| If you use style sheets, make sure that the page can be viewed when style sheets are not applied or supported. | Pages can still be read without CSS formatting |
| If you use any tools that provide dynamic content using scripts you must provide an alternative version that is equivalent. | We use the <NOSCRIPT></NOSCRIPT> tags to direct users to the alternative content |
| Do not allow the screen or screen elements to flicker on and off. | Working towards this |
| If you use an image map you must provide an alternative means for users to access the information. | We do not use image maps |
| If you use a table to actually organize data, you must identify row and column headers and for data tables with two or more logical levels of row or column headers you must use code to associate data cells and header cells | Working towards this |
| Do not use frames in webpages. They are not supported. | We do not use frames |
| Make sure that a contact person is identified on each of your pages for users who cannot access the information on that page. | Users can e-mail the webmaster to request information |
| A page should take no longer than 20 seconds to load on a 28.8 kbps connection. If pages take longer than 20 seconds, then content should be compressed or broken into multiple pages to speed the display. | No page takes longer than 20 seconds to load |
| Priority 2 (Level AA): | |
| Use the College's Style Sheet, Header and Footer (or modified versions of them) to control layout and presentation. | We use CSS but in a way that the user can over-ride our stylesheet |
| Do not use pages that auto-refresh, auto-redirect or links that open pages in new browser windows. | We do not use pages that auto-refresh, auto-redirect. In some cases we open pages in new browser windows. |
| Provide a site map or table of contents for your site. | We provide a sitemap |
| Use proper markup for headings, lists and quotations. | We use proper markup |
| Priority 3 (Level AAA): | |
| If you use an acronym or an abbreviation, identify its meaning in its first usage. | We identify meaning upon first usage of an acronym or abbreviation |
| If you have two links adjacent to each other, place a non-link, printable character between them. | We don't use adjacent links often but when we do we seperate them |
| Provide summaries for tables. | We are working towards this |
| Do not place text in side-by-side columns, as in newspaper layouts. | We do not do this in most cases |
| When using forms, use a logical tab order, adjacent label layouts and default values for all form fields. | We do so when its appropriate |
