Yes, this is an article about web standards, but if you bear with me, I’ll try and keep things interesting. Web standards are something that we work on a lot with EditLive!. I believe it’s part of our job as developers of an HTML text editor to deal with these standards in such a way that you don’t have to. That requires you to trust us, or whichever other HTML text editor you choose to license, to do right by your content and not just meet the standard, but meet the best possible interpretation of the standard.
That sounds like pretty high-minded, theoretical stuff, so let me bring things back down to reality with an example. Several years ago we were working with a major retailer who was going through an extensive rebranding exercise. The exercise involved changing the colour scheme on several of their web properties. Now while their HTML and CSS was all standards compliant their previous open source HTML text editor hadn’t been configured well and had embedded massive amounts of inline styling, particularly with content imported from Microsoft Word. What should have been a quick update of their site’s CSS turned into months of work to update a huge amount of content to remove the inline styling they didn’t even know they were creating. They had rightly trusted their rich text editor to create standards compliant content – which it did – but how it did that was so inflexible it cost them months of work and delays.
What should have been a quick update of their site’s CSS turned into months of work to update a huge amount of content to remove the inline styling they didn’t even know they were creating. They had rightly trusted their rich text editor to create standards compliant content – which it did – but how it did that was so inflexible it cost them months of work and delays.
So how does EditLive! use web standards and how do we ensure that you’re always creating compliant, flexible web content that will work everywhere? For us, it came down to the consistent and considered application of web standards in everything the editor does. Here are the key things that EditLive! does to ensure your content’s standards compliance:
- Clean content import from Microsoft Word and Excel – In addition to ensuring content is standards compliant EditLive! by default also ensures that it’s cleaned of all inline styling.
- Consistent HTML – The markup produced by an HTML text editor needs to be consistent irrespective of browser or usage. Consistent HTML can be consistently and easily styled.
- CSS, not deprecated HTML – Wherever possible EditLive! uses CSS properties instead of equivalent deprecated HTML attributes. This modern approach maximizes the compatibility of your HTML on modern devices and ensures a consistent approach to styling.
- Accessibility check-as-you-type – As you type, EditLive!’s accessibility tools will make it easy to create content compliant with WCAG and Section 508 guidelines.
- MathML for equations – With EditLive!’s equation editor, you can write standards-compliant Mathematical Markup Language (MathML) that can be processed by another server or used with another browser plugin.
- Syntax highlighting – Even if you’re working in code view EditLive! assists in producing compliant HTML with syntax highlighting enabling you to immediately see unterminated tags or attribute values.
When you’re selecting an HTML text editor, take the time to review their standards support as not all editors are created equal. Investing the time in evaluating the quality of the markup produced by an editor could save you a lot of time in future.
EditLive!’s consistent and considered approach to web standards mean that you’re going to reliable, consistent, stylable markup that works on your site now and will continue to work well into the future, no matter how many colour schemes your website goes through.