Dynamic pages are created by pulling repetitive chunks of HTML code from different sources. For instance, this site uses a database engine to insert the same header and footer on each page of this Web site.
Dynamic pages or content management systems can be a convenient way to make sure navigation blocks, skip navigation links, ALT tags in headers and so forth are consistently implemented on each page. However, almost all dynamic pages require access to special server set-ups, so require input from server administrators or programmers.
Implement recommendations from the WAI-ARIA working group whenever possible. ARIA support is available in Firefox 3, Opera 9.5 and is scheduled to be available in Internet Explorer 8 (in beta as of April 2008) as well as Safari 4 (in beta).
Make sure all HTML code chunks include accessibility tags such as ALT tags, TH tags for data tables, LABEL tags for forms, and so forth.
If your system uses Javascript links, make sure to include a link to a text-only alternative navigational system such as a Sitemap.
Avoid using arbitrary database numbers for ALT tags, TITLE tags, FRAME tags and other text-alternative accessibility tags. Ideally, a content management system would allow users to enter an ALT tag text for an uploaded image.
<img src="1103AB43.jpg" alt="Image_1103AB43.jpg" >
A screen reader would say Image 1103AB43.
If possible, use a script to convert dynamic page style links (e.g. www.mysite.psu/main.php?id=11) to more traditional type links (e.g. www.mysite.psu/page11.html) They are less likely to encounter compatibility issues with screen readers or older browsers.
If you wish to experiment with dynamic page creation, the simplest technology is probably Server Side Includes. The rest require either extensive programming, access to a database backend or both.