Welcome to the forums, ak0787777.
Some general information for new members.
If you have not done so already, please read our posting guidelines.
Specifically, please note that we request a “working page” that demonstrates the issue so we can see the same thing on our computer that you see on yours. A “working page” begins with a <!doctype ...>. It continues with the <head> section which addresses any essential resources that your page needs and may include any on-page CSS between <style> tags. Next will come the <body> portion of the page in which the HTML that demonstrates the issue will reside. Just before the </body> close body portion of the page we normally expect to find JS or links to external JS routines that would not have been appropriate to include in the <head> of the page. Finally, the page should end with the </html> close HTML tag. The code should be validated before posting. Neatly formatting the code (eg: Tidy) is a plus for everyone.
Example “working page”:
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width,initial-scale=1.0">
<script src="https://code.jquery.com/jquery-1.11.1.min.js"></script> <!-- IF jQuery is used -->
<link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.2/css/bootstrap.min.css"> <!-- IF Bootstrap is used, call correct version -->
<link rel="stylesheet" href="css/stylesheet.css"> <!-- local stylesheet, can override preceeding stylesheets-->
<title>required</title>
<style>
on-page css here, if any, can override preceeding stylesheets
</style>
</head>
<body>
HTML here
<script>
on-page JS here, if any
</script>
</body>
</html>
Most of the code that we post in the HTML/CSS forum will be in the form of a “working page” so there are plenty of examples for you to see.
Be sure that the URLs that call resources are full URLs or that the resources, such as scripts or images, are attached to your post.
You can create a CodePen or JSFiddle that demonstrates the issue and includes surroundind (framing) page code so we can understand how and where the troublesome code exists on the page.
Finally, you could choose to post a link to your test site where we can see your code in action.
You can add screen shots that help demonstrate the issue. They do not substitute for code, though. Don’t expect us to copy your code from a screenshot. 
Please be sure to give us feedback about our efforts. We want to know if our efforts are helpful or not.
Thank you for reading and we hope you enjoy your visits here. 