I would like to have a WordPress plugin installed that takes the content from the WordPress site and converts it to a 'standard' HTML website with a different look/feel. Kind of like the WPTouch plugin converts data to a mobile-friendly format, I want this plugin to take the content from the website and recreate the site in a very simplistic layout (as simple as the TwentyThirteen theme).
Within the design of the new 'look/feel' that is created:
- The plugin will create a notification bar above the header that indicates that someone can click on that link to access the alternate site.
- The site will be simply text (with only the site header and/or logo carrying over to the new site)
- Be sure carry over the ALT TAG for very image, video file, audio file, plug-in, etc. if there are any that carry over
- If an image is used as a link on the original page, make sure the new site has that link but that the ALT TAG identifies the new link and list the link destination
- If videos are present on the main site, create a link to the video rather than embedding it and add a link to the media player download and text transcript (if provided)
- The page should provide alternative links to the Image Map
- The <area> tags must contain an alt attribute
- Data tables have the column and row headers appropriately identified (using the <th> tag)
- Tables used strictly for layout purposes do NOT have header rows or columns
- Table cells are associated with the appropriate headers (e.g. with the id, headers, scope and/or axis HTML attributes)
- A link is provided to a disability-accessible page where the plug-in can be downloaded
- All Java applets, scripts and plug-ins (including Acrobat PDF files and PowerPoint files, etc.) and the content within them are accessible to assistive technologies (screen/text readers, etc.), or else an alternative means of accessing equivalent content is provided
- When form controls are text input fields use the LABEL element
- When text is not available use the title attribute
- Include any special instructions within field labels
- Make sure that form fields are in a logical tab order
- Include a ‘Skip Navigation' button to help those using text readers
- If the site is set to automatically refresh every X seconds, disable the refresh and provide a link for them to click to refresh the content of the page.
- Use titles, context, and other heading structures to help users navigate complex pages or elements (such as webpages that use frames)
- Make sure that websites are designed so they can be displayed using the color and font settings of each visitor’s browser and operating system.
- Make sure that any navigational drop down items do not drop down based on a 'hover', but rather based on a click. So, if you have subnav in the main nav bar, the nav bar will have an indicator that there is subnav (upside down chevrons, maybe), then the user has to click the main nav bar to open the drop downs and the drop downs will stay open until the user clicks again. Any subsubnavs will work the same way.
The plugin must have the ability to support a subscription model -- meaning that it should check the database of the plugin provider to be sure that the plugin has been validated and the subscription is still active.
This will allow me to charge $X/month or $X/year for the plugin to be active and receive updates.
The plugin will be allowed to be active on only one website at a time.
If the plugin does not validate, or if it is trying to update from a website other than the initial website from where it was installed, then the plugin will not activate and will not work on the client site. It should trigger them to go to an 'activation website' where they can activate the plugin for the site for which it is installed.
The plugin should work on self-hosted WP sites (functionality with [url removed, login to view] or WPMU would be nice, but not necessary).